home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Nebula 2
/
Nebula Two.iso
/
SourceCode
/
MiscKit1.7.1
/
MiscKitArchive.mbox
/
mbox
/
000170_misckit-reques…aska.et.byu.edu_Thu Apr 7 00:56:49 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-10-30
|
4KB
Return-Path: <misckit-request@alaska.et.byu.edu>
Received: from alaska.et.byu.edu by darth.byu.edu (NX5.67d/NX3.0M)
id AA12212; Thu, 7 Apr 94 00:56:39 -0600
Received: from darth.byu.edu by alaska.et.byu.edu; Thu, 7 Apr 1994 00:52:10 -0600
Received: by darth.byu.edu (NX5.67d/NX3.0M)
id AA12169; Thu, 7 Apr 94 00:13:44 -0600
Date: Thu, 7 Apr 94 00:13:44 -0600
From: Don Yacktman <don@darth.byu.edu>
Message-Id: <9404070613.AA12169@darth.byu.edu>
Received: by NeXT.Mailer (1.100.RR)
Received: by NeXT Mailer (1.100.RR)
To: misckit@alaska.et.byu.edu
Subject: Re: MiscKit.pkg
Reply-To: don@darth.byu.edu
> First let me congratulate everyone that's participated in the MiscKit project
> and made it such a smashing success.
There sure have been some great submissions...and I've just
had some more cool stuff come in. I'd like to once again
publically thank all the contributors. There's been a lot of
effort put into the kit--by over 25 different individuals!
Every one of them gets my heartfelt thanks, that's for sure.
I'm using your objects in my projects, that's for sure. :-)
> Now, someone (Don?) tell me why there isn't a MiscKit.pkg binary package
> out there for installations to /LocalDeveloper/.
I brought this point up in January...with the question of "who would want this?"
At the time the concensus was "we are all developers and are quite capable
of typing 'make', thank you very much." So, since it would take a bit more
effort to create a package (though not much more) I decided it wasn't worth
the bother to do so, since no one actually wanted it.
I will now repeat the question: Who would want a .pkg with the binaries?
The file tree would still be relocatable: the precomp headers can be generated
by a post_install script with no trouble whatsoever. The package would set to
install in either ~/Library or in /LocalDeveloper. (It would make more sense to
have ~/Developer, but that's not a generally accepted convention, and ~/Library
would still work OK...)
There is now at least one more argument for doing this: doing a build of the kit
is (1) a lot more time consuming and (2) requires one huge load of disk space.
If you don't have the time and/or the disk, the package might be the only way to
get yourself a MiscKit without only compiling sections of it. As the kit grows in
size, it could eventually reach the point where it will no longer build on your
machine...so keep that in mind, even though it's not a problem for most of you
at the moment. (In my case, I know it would be a lot more convenient to have
more HD space...I have other projects that take as much space as the MiscKit
to build, so I have to clean one to work on the other and it's a pain.)
> P.S. Who's goofy voice was that in the makefile audio alerts? Just kidding,
> I thought it was cool to have make talk to me. :)
You're right. It's goofy, and about as maximally annoying as these things get. Now
it also runs open to pop up the README.rtf. I'm gonna clutter your screen, too. :-)
Well, as most guessed, correctly, it is in fact me. I hate it, myself. The reason I put
it there was because I found I was wasting half my day for 2-3 days after each
release answering questions that are IMHO adequately answered in the README
file. In fact, since I put that there, ALL the questions that are answered in the README
have stopped. I think it worked. As you know, if you read the README, :-) you can
turn them off quite easily. That's one of the first things the README tells you how
to do, in fact. :-) Believe me, I always turn them off while working on the kit. Of
course one of these days I just know I'm going to make a release and forget to turn
them back on. That just seems like something I'd do, flake that I am... (oh, and you
can also turn off the README popping up on the screen if that bugs you)
Anyway, has the general opinion on binaries changed? I know that many people
simply "trust" code that they typed "make" on themselves, where they won't trust
me to type "make" for them. That may be a very good thing, actually. :-) If I did do
a .pkg, I would still do a parallel release just like the current releases. And the .pkg
would still contain the full source tree, as well, of course.
---
Later,
-Don Yacktman
Don_Yacktman@byu.edu